Dynamic transaction card optimization

ABSTRACT

The present disclosure relates to devices and methods relating to an optimized electronic transaction card where various data inputs associated with a dynamic transaction card optimize operational configurations and/or a user experience of the dynamic transaction card to extend an energy storage life of the dynamic transaction card, promote various behaviors, and/or detect system and/or device defects. A dynamic transaction card may include a dynamic transaction card with various configuration and/or functionality that use the power components (e.g., printed circuit board (PCB), energy storage component, battery, and/or the like) of the dynamic transaction card. The configuration and/or functionality data may include, for example, sensor input, connection data, transaction data, display data, and/or the like. The configuration and/or functionality data may then be used to determine optimal configuration settings.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/270,384 entitled “Electronic Card Optimization” filed Dec. 21, 2015;and U.S. Provisional Patent Application No. 62/147,568, filed on Apr.14, 2015. The entire contents of these applications are incorporatedherein by reference.

This application is related, U.S. application Ser. No. 14/338,423,entitled “System and Method for Exchanging Data with Smart Cards” filedJul. 23, 2014, which claims the benefit of U.S. Provisional ApplicationNo. 61/857,443 filed on Jul. 23, 2013; and U.S. application Ser. No.______, entitled “Transaction Card Power Management” filed Apr. 14,2016, which claims the benefit of U.S. Provisional Application No.62/266,324, filed Dec. 11, 2015, U.S. Provisional Application No.62/270,307 filed Dec. 21, 2015, and U.S. Provisional Application No.62/305,599, filed Mar. 9, 2016. The entire contents of theseapplications are incorporated herein by reference.

FIELD OF THE DISCLOSURE

The present disclosure relates to an optimized dynamic transaction cardwhere various inputs optimize operational configurations and/or a userexperience of the dynamic transaction card, detect system and/or devicedefects, and extend an energy storage life of the dynamic transactioncard.

BACKGROUND OF THE DISCLOSURE

A smart card includes a variety of operational configurations, such aslighting configurations, display configurations, and sensorconfigurations and performs a number of functions. Each of theseconfigurations and/or functions depletes the power components of thedynamic transaction card and may be altered in order to affect thedepletion of power components. Additionally, these electronicconfigurations and/or functions may negatively affect a user experienceand/or user behaviors associated with the card

These and other drawbacks exist.

SUMMARY OF THE DISCLOSURE

Various embodiments of the present disclosure provide devices andmethods relating to an optimized electronic transaction card wherevarious data inputs associated with a dynamic transaction card optimizeoperational configurations and/or a user experience of the dynamictransaction card to extend an energy storage life of the dynamictransaction card, promote various behaviors, and/or detect system and/ordevice defects.

As referred to herein, a dynamic transaction card may include a dynamictransaction card with various configurations and/or functionality thatuse the power components (e.g., printed circuit board (PCB), energystorage component, battery, and/or the like) of the dynamic transactioncard. The configuration and/or functionality data associated with thepower components may include, for example, sensor input (e.g., a numberof taps, a number of double taps, time between double taps, fingerprint,PIN or password input, light sensor threshold, and/or the like),connection data (e.g., connection attempts, connection length, time inadvertising mode, time in scanning mode, and/or the like), transactiondata (e.g., contactless transaction attempts, time per contactlesstransaction, contact transaction attempts, time per contacttransactions, and/or the like), display data (e.g., light brightness,light active time, display brightness, display contrast, display activetime, and/or the like), and/or the like.

The configuration and/or functionality data may be determined and/orstored by the dynamic transaction card, transmitted to a user device,stored in a user device, transmitted to a backend server, and/or storedin a backend server. The configuration and/or functionality data may beused by the dynamic transaction card, user device, and/or backend serverto determine optimal configurations and/or user experiences for thedynamic transaction card and/or additional dynamic transaction cards,detect system and/or device defects, promote a particular user behavior,and/or extend an energy storage life of one or more dynamic transactioncards.

Optimal configurations may be determined by linear regression, logisticregression, ridge regression, lasso regression, Bayesian regression,machine learning algorithms, and/or the like. Optimal configurations maybe determined on a device-by-device basis, a grouping of device (e.g.,grouping by demographic data, grouping by geolocation data, grouping byusage, grouping by software revisions, grouping by hardware differencessuch as a device generation, and/or the like), and or the entirety ofdynamic transaction cards. System defects may be determined bydetermining and detecting outlier data associated with transaction cardtransaction data. Device defects may be determined by determining anddetecting outlier data associated with any configuration and/orfunctionality data for a particular device.

Extended energy storage life may be determined based on the optimalconfigurations. For example, the configuration and/or functionality datamay be optimized in order to determine a maximum energy storage life fora dynamic transaction card, promote various behaviors, and/or detectsystem and/or device defects. Configuration and/or functionality datamay be optimized in order to determine a maximum transaction attempts.Without the data generated by the dynamic transaction card (s), thedynamic transaction cards may not be optimized in order to determinedefects, promote user behaviors, and/or optimize an energy storage life.

Transmission of data between a dynamic transaction card and a userdevice and/or backend system may be performed at any interval. Forexample, transmission of data may occur on an hourly, daily, and/orother timed interval. Transmission of data may occur on an event basis,such as a number of transactions, a number of power-ups of a dynamictransaction card, a number of waking-ups of a dynamic transaction card,and/or the like.

Optimization of data may be performed at any interval. For example,optimization of data may occur on an hourly, daily, and/or other timedinterval. Optimization of data may occur on an event basis, such as anumber of transactions, a number of power-ups of a dynamic transactioncard, a number of waking-ups of a dynamic transaction card, and/or thelike.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the present disclosure, together with furtherobjects and advantages, may best be understood by reference to thefollowing description taken in conjunction with the accompanyingdrawings, in the several Figures of which like reference numeralsidentify like elements, and in which:

FIG. 1 depicts an example embodiment of a system that uses dataassociated with a dynamic transaction card as input to optimizeoperational configurations and/or a user experience of the dynamictransaction card, detect system and/or device defects, and extend anenergy storage life of the dynamic transaction card, according toembodiments of the disclosure;

FIG. 2 depicts an example embodiment of a dynamic transaction card thatcreates, monitors, and/or transmits data associated with the dynamictransaction card as input to optimize operational configurations and/ora user experience of the dynamic transaction card, detect system and/ordevice defects, and extend an energy storage life of the dynamictransaction card, according to embodiments of the disclosure;

FIG. 3 depicts an example embodiment of a dynamic transaction card thatcreates, monitors, and/or transmits data associated with the dynamictransaction card as input to optimize operational configurations and/ora user experience of the dynamic transaction card, detect system and/ordevice defects, and extend an energy storage life of the dynamictransaction card, according to embodiments of the disclosure;

FIG. 4 depicts an example PoS system that may interact with a dynamictransaction card that creates, monitors, and/or transmits dataassociated with the dynamic transaction card as input to optimizeoperational configurations and/or a user experience of the dynamictransaction card, detect system and/or device defects, and extend anenergy storage life of the dynamic transaction card, according toembodiments of the disclosure;

FIG. 5 depicts an example backend system and user device that mayinteract with a dynamic transaction card to create, monitor, and/ortransmit data associated with the dynamic transaction card as input tooptimize operational configurations and/or a user experience of thedynamic transaction card, detect system and/or device defects, andextend an energy storage life of the dynamic transaction card, accordingto embodiments of the disclosure;

FIG. 6 depicts an example method that uses data associated with adynamic transaction card as input to optimize operational configurationsand/or a user experience of the dynamic transaction card, detect systemand/or device defects, and extend an energy storage life of the dynamictransaction card, according to embodiments of the disclosure; and

FIG. 7 depicts an example method that uses data associated with adynamic transaction card as input to optimize operational configurationsand/or a user experience of the dynamic transaction card, detect systemand/or device defects, and extend an energy storage life of the dynamictransaction card, according to embodiments of the disclosure.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The following description is intended to convey a thorough understandingof the embodiments described by providing a number of specific exampleembodiments and details involving data associated with a dynamictransaction card that may be used as input to optimize operationalconfigurations and/or a user experience of the dynamic transaction card,detect system and/or device defects, and extend an energy storage lifeof the dynamic transaction card. It should be appreciated, however, thatthe present disclosure is not limited to these specific embodiments anddetails, which are examples only. It is further understood that onepossessing ordinary skill in the art, in light of known systems andmethods, would appreciate the use of the invention for its intendedpurposes and benefits in any number of alternative embodiments,depending on specific design and other needs. A dynamic transactioncard, mobile device, and PoS are used as examples for the disclosure.The disclosure is not intended to be limited to dynamic transactioncards, mobile devices, or PoS systems only.

Additionally, the use of “mobile device” in the examples throughout thisapplication is only by way of example. Any type of device capable ofcommunicating with a dynamic transaction card may also be used,including, for example, personal computers, tablets, gaming systems,televisions, or the like.

FIG. 1 depicts an example system 100 including a dynamic transactioncard that generates data that may be used as input to optimizeoperational configurations and/or a user experience of the dynamictransaction card, detect system and/or device defects, and extend anenergy storage life of the dynamic transaction card. As shown in FIG. 1,an example system 100 may include one or more dynamic transaction cards120, one or more backend systems 130, one or more mobile devices 140,and one or more merchant systems 150 connected over one or more networks110.

For example, network 110 may be one or more of a wireless network, awired network or any combination of wireless network and wired network.For example, network 110 may include one or more of a fiber opticsnetwork, a passive optical network, a cable network, an Internetnetwork, a satellite network, a wireless LAN, a Global System for MobileCommunication (“GSM”), a Personal Communication Service (“PCS”), aPersonal Area Network (“PAN”), Wireless Application Protocol (WAP),Multimedia Messaging Service (MMS), Enhanced Messaging Service (EMS),Short Message Service (SMS), Time Division Multiplexing (TDM) basedsystems, Code Division Multiple Access (CDMA) based systems, D-AMPS,Wi-Fi, Fixed Wireless Data, IEEE 802.11b, 802.15.1, 802.11n and 802.11g,a Bluetooth network, or any other wired or wireless network fortransmitting and receiving a data signal.

In addition, network 110 may include, without limitation, telephonelines, fiber optics, IEEE Ethernet 902.3, a wide area network (“WAN”), alocal area network (“LAN”), a wireless personal area network (“WPAN”),or a global network such as the Internet. Also network 110 may supportan Internet network, a wireless communication network, a cellularnetwork, or the like, or any combination thereof. Network 110 mayfurther include one network, or any number of the example types ofnetworks mentioned above, operating as a stand-alone network or incooperation with each other. Network 110 may utilize one or moreprotocols of one or more network elements to which they arecommunicatively coupled. Network 110 may translate to or from otherprotocols to one or more protocols of network devices. Although network110 is depicted as a single network, it should be appreciated thataccording to one or more embodiments, network 110 may comprise aplurality of interconnected networks, such as, for example, theInternet, a service provider's network, a cable television network,corporate networks, and home networks.

Mobile device 140 and/or merchant system 150 may include, for example,one or more mobile devices, such as, for example, personal digitalassistants (PDA), tablet computers and/or electronic readers (e.g.,iPad, Kindle Fire, Playbook, Touchpad, etc.), wearable devices (e.g.,Google Glass), telephony devices, smartphones, cameras, music playingdevices (e.g., iPod, etc.), televisions, set-top-box devices, and thelike.

Backend systems 130, mobile devices 140, and/or merchant system 150 alsomay include a network-enabled computer system and/or device. As referredto herein, a network-enabled computer system and/or device may include,but is not limited to: e.g., any computer device, or communicationsdevice including, e.g., a server, a network appliance, a personalcomputer (PC), a workstation, a mobile device, a phone, a handheld PC, apersonal digital assistant (PDA), a thin client, a fat client, anInternet browser, or other device. The network-enabled computer systemsmay execute one or more software applications to, for example, receivedata as input from an entity accessing the network-enabled computersystem, process received data, transmit data over a network, and receivedata over a network. For example, merchant system 150 may include, forexample, components illustrated in FIG. 4.

Backend systems 130, mobile devices 140, and/or merchant system 150 mayinclude at least one central processing unit (CPU), which may beconfigured to execute computer program instructions to perform variousprocesses and methods. Backend systems 130, mobile devices 140, and/ormerchant system 150 may include data storage, including for example,random access memory (RAM) and read only memory (ROM), which may beconfigured to access and store data and information and computer programinstructions. Data storage may also include storage media or othersuitable type of memory (e.g., such as, for example, RAM, ROM,programmable read-only memory (PROM), erasable programmable read-onlymemory (EPROM), electrically erasable programmable read-only memory(EEPROM), magnetic disks, optical disks, floppy disks, hard disks,removable cartridges, flash drives, any type of tangible andnon-transitory storage medium), where the files that comprise anoperating system, application programs including, for example, webbrowser application, email application and/or other applications, anddata files may be stored. The data storage of the network-enabledcomputer systems may include electronic information, files, anddocuments stored in various ways, including, for example, a flat file,indexed file, hierarchical database, relational database, such as adatabase created and maintained with software from, for example, Oracle®Corporation, Microsoft® Excel file, Microsoft® Access file, a solidstate storage device, which may include an all flash array, a hybridarray, or a server-side product, enterprise storage, which may includeonline or cloud storage, or any other storage mechanism.

Backend systems 130, mobile devices 140, and/or merchant system 150 mayfurther include, for example, a processor, which may be severalprocessors, a single processor, or a single device having multipleprocessors. Although depicted as single elements, it should beappreciated that according to one or more embodiments, backend systems130, mobile devices 140, and/or merchant system 150 may comprise aplurality of backend systems 130, mobile devices 140, and/or merchantsystems 150.

Backend systems 130, mobile devices 140, and/or merchant system 150 mayfurther include data storage. The data storage may include electronicinformation, files, and documents stored in various ways, including, forexample, a flat file, indexed file, hierarchical database, relationaldatabase, such as a database created and maintained with software from,for example, Oracle® Corporation, Microsoft® Excel file, Microsoft®Access file, a solid state storage device, which may include an allflash array, a hybrid array, or a server-side product, enterprisestorage, which may include online or cloud storage or any other storagemechanism.

As shown in FIG. 1, each backend systems 130, mobile devices 140, and/ormerchant system 150 may include various components. These components maybe understood to refer to computer executable software, firmware,hardware, and/or various combinations thereof. It is noted that where acomponent includes software and/or firmware, the components isconfigured to affect the hardware elements of an associated system. Itis further noted that the components shown and described herein areintended as examples. The components may be combined, integrated,separated, or duplicated to support various applications. Also, afunction described herein as being performed at a particular componentmay be performed at one or more other components and by one or moreother devices instead of or in addition to the function performed at theparticular component.

As depicted in FIG. 1, system 100 may include a dynamic transaction card120. A dynamic transaction card 120 may include an electronic display todisplay alerts, notifications, and/or other output via a display and/orLED lighting 126 and/or receive input to interact with the electronicdevice 120 via, for example, a sensor 124. Dynamic transaction card 120also may be composed of various materials that enable the entireexterior surface of dynamic transaction card 120 to act as a sensor.

A dynamic transaction card 120 may be able to communicate with, forexample, a mobile device using RFID, Bluetooth, NFC, WiFi Direct, and/orother related technologies. For example, communications between adynamic transaction card 120 and a mobile device 140 may includemethods, systems, and devices as described in U.S. patent applicationSer. No. 14/338,423 filed on Jul. 23, 2014, the entire contents of whichis incorporated herein by reference.

A dynamic transaction card 120 may be able to communicate with amerchant system 150 via contacts 122 (e.g., EMV chip contacts) locatedon the dynamic transaction card 120. A dynamic transaction card 120 mayalso include hardware components to provide contactless payments and/orcommunications. For example, a dynamic transaction card 120 may includean output layer, an outer protective layer, potting, application (e.g.,a Java Applet), application integration (e.g., Java Applet integration),an EMV chip 122, one or more sensors, a display, a display driver,firmware, a bootloader, a microcontroller, one or more antenna, anenergy storage component, power management, a flexible PCB, a chassis,and/or card backing as illustrated in FIGS. 2 and 3. An EMV chip 122 maybe embedded in the electronic device 120 may include a number ofcontacts that may be connected and activated using an interface device.

FIG. 2 depicts an example dynamic transaction card 200. As shown in FIG.2, dynamic transaction card 200 may include a top output layer 202. Thetop output layer may be a film covering, a plastic covering, and/or thelike. The top output layer 202 may be constructed of scratch-resistantand/or scratch-proof materials. Materials that may be used as a topouter layer 202 may include polyvinyl chloride (PVC), polylactic acid(PLA), acrylonitrile butadiene styrene (ABS), polyethlene terephthalate(PET), Polyethylene terephthalate glycol-modified (PET-G), and/or thelike. A dynamic transaction card 200 may further include a topprotective layer 204, such as a clear scratch-resistant coating and/orscratch-proof material to protect the underlying components. Forexample, various scratch-resistant materials include materials coatedwith a scratch resistant chemical coating, such as a UV curable chemicalcoating. Scratch-proof materials may include a mineral glass, a sapphireglass material, PVC, PET, and/or PET-G.

A dynamic transaction card may include a potting 206 or filler epoxyaround the electrical components to provide strength and/or waterresistance. A potting 206 may include a light guide, which may beconstructed of optical grade materials such as acrylic, resin,polycarbonate, epoxies, and/or glass. Potting 206 may also includeinjection molding, such as over molding and/or multi-shot to encapsulatethe internal components of card 200. For example, injection molding mayinclude ABS, thermoplastic elastomers (TPE), thermoplastic vulcanizate(TPV), thermoplastic polyurethane (TPU), PET, polycarbonates (PC),and/or silicone.

A dynamic transaction card 200 may further include a Java Applet 208 andJava Applet integration 210. Although a Java Applet 208 is used throughthe specification, any other similar type of code application may beused. Moreover, although Java Applet integration 210 is used throughoutthis specification, any type of interface may be used to allow themicrocontroller to interact with the EMV chip. A Java Applet 208 mayinclude code that executes payments, such as payment made using an EMVchip. A Java Applet 208 may include account-provider specific code toexecute display functionality specific to the account provider. JavaApplet integration 210 may include coded interfaces to allow themicrocontroller to interact with the EMV chip 212.

An EMV chip 212 may include a number of contacts that may interact witha terminal, such as a merchant system 150. During an EMV interaction,application cryptograms may be used to send and receive data packetsbetween the dynamic transaction card 200 and a terminal. For example,data packets may include user authentication information which anacquisition system and/or issuing financial institution may use toauthenticate a transaction card 200 during a transaction. Variouscryptographic protocols and/or methods may be used in this datatransmission and reception process. Moreover, during a transactionissuing financial institutions and/or acquisition systems may returnscript commands to the EMV chip 212 via a terminal. These scriptcommands and/or data packets may be transmitted between parties over anetwork. Script commands may be used, for example, to blocktransactions, change transaction data stored on the EMV chip (e.g.,transaction history, account limits, account balance, and/or the like).Offline data authentication may also take place using, for examplepublic key cryptography to perform payment data authentication. Forexample, offline data authentication may use Static Data Authentication(SDA), Dynamic Data Authentication (DDA), and/or Combined DataAuthentication (CDA).

Dynamic transaction card 200 may also include one or more sensors 214 toreceive input. Sensors 214 may include an activation sensor and/or anoperation sensor, which may be combined and/or separate. An activationsensor may activate the dynamic transaction card 200 and an operationsensor may instruct the dynamic transaction card 200 to perform anaction based on the received input. An activation sensor may require asecurity input, such as a biometric input (e.g., fingerprint, eye scan,voice recognition, and/or the like), input indicative of a paired mobiledevice (e.g., BLE and/or Bluetooth pairing), input indicative of apassword (e.g., a password received via a sensor on the dynamictransaction card and/or a password received on a paired mobile device),and/or the like. An operation sensor may change a display 216 based onreceived input, conduct a transaction via, for example an EMV chip 212and/or contactless payment technologies based on received input, attempta pairing of a card 200 and a mobile device, and/or the like.

By way of example, a sensor 214 may include a capacitive touch sensor, apiezoelectric sensor, load cells, a light sensor, a temperature sensor,a resistive touchscreen, including for example an analogue matrix real(AMR) sensors, and/or the like. Sensors 214 may include accelerometersto detect motion input.

Although the sensor 214 is depicted at a particular spot in thetransaction card 200, a sensor 214 may be placed at any portion of thecard to detect, for example, touch, light, heat, energy, and/or thelike. For example, a sensor may be placed around the outer edges of adynamic transaction card 200 or at any spot within the dynamictransaction card 200. Sensor 214 also may include the entire exteriorsurface of transaction card 200.

A display 216 may be provided within the transaction card 200. Althoughthe display as shown includes, for example, a dot matrix display, anumber of other display options may be included in the transaction card200. For example, lighting, such as LED lighting, OLED lighting, and/orthe like, may be used as display components. Display components may alsoinclude electronic paper, Mirasol, TF LCD, Quantum Dot Display, and/orthe like. Where lighting is used, various lighting technologies may beused to create a display that indicates a number of things to acardholder. For example, edge lighting may be used to create a specificvisual component in the display. A number of LED or OLED lights may beused to illuminate various portions of the display in order to outputinformation to a card holder.

By way of example, a display 216 may be illuminated using a particularcolor to relay to the cardholder balance information of an accountassociated with a transaction card, such as an RGB LED matrix paneland/or RGB LED displays. A red light display may indicate that theaccount balance is within a first predetermined dollar amount or a firstpredetermined percentage of the total spending limit, a particularbudget, a particular budget category, and/or the like. A yellow lightdisplay may indicate that the account balance is within a secondpredetermined dollar amount or a second predetermined percentage of thetotal spending limit, a particular budget, a particular budget category,and/or the like. A green light display may indicate that the accountbalance is within a third predetermined dollar amount or a thirdpredetermined percentage of the total spending limit, a particularbudget, a particular budget category, and/or the like. Various colorsand or number of categories may be used to output this information to acardholder. A display 216 may include other display component, such as,for example, LCD technology, ePaper technology (e.g., e-ink), vacuumflorescent display technology, and/or the like.

By way of example, a display may include a number of LED or OLED lightsthat may be lit in a particular pattern to indicate transaction and/oraccount information. For example, a display may include a circle,semicircle, or other shape of LED or OLED lighting, where the number oflights illuminated indicates a dollar amount or a percentage of thetotal spending limit, a particular budget, a particular budget category,and/or the like.

A display may be altered and/or modified, for example, for example,where dynamic transaction card 200 includes a debit account, a firstcredit account, and a second credit account, display components 216 mayreflect the card number, security code, expiration date, and/or othernecessary data indicative of the account (e.g., second credit account)that is being used to execute a transaction. A display may be alteredand/or modified when, for example, a dynamic transaction card 200receives new card data and/or new account data from an account holder'smobile device via a wireless connection. For example, where an accounthas been marked as associated with fraudulent activity, an accountholder and/or issuing financial institution may deactivate the cardassociated with the account and issue a new card. Accordingly, new carddata may be transmitted from the issuing financial institution to, forexample, an account holder's mobile device via a network, and then froman account holder's mobile device to electronic card 200 via a wirelessconnection. A display may also be altered and/or modified whenelectronic card 200 activates a new account. For example, when anaccount holder applies for a new account (e.g., a new credit cardaccount, a new checking account, and/or the like), if approved, newaccount data may be transmitted to electronic card 200. New account datamay be received at an account holder's mobile device from an issuingfinancial institution via a network (e.g., using a mobile application,mobile optimized website, and/or the like). New account data may then betransmitted from an account holder's mobile device to electronic card200 via a wireless connection (e.g., BLE, RFID, NFC, WiFi, and/or thelike) or a contact connection (e.g., using a terminal in contact with anEMV chip and/or other microchip).

A dynamic transaction card 200 may include a display driver 218 thattranslates instructions from a microcontroller 224 into display imagesto be displayed using display components 216. A display driver 218 mayinclude an integrated circuit (IC), a state machine, and/or the likethat provides an interface function between the display and themicrocontroller 224. A display driver 218 may include memory (e.g., RAM,Flash, ROM, and/or the like) and/or firmware that includes font displaydata.

A dynamic transaction card 200 may include firmware 220 and/or abootloader 222. A bootloader 222 may include code to be executed as anelectronic card 200 is activated and before any operating system,firmware, or other code is executed on the dynamic transaction card 200.A bootloader may be activated via a sensor 214 and energy storagecomponent 228 of the dynamic transaction card 200. Bootloader 222 may beactivated and/or load an application and/or program upon detection thatcard 200 has been inserted into a terminal, charger, and/or the like.Bootloader 222 may be activated using only one technique describedherein, using multiple techniques described herein, and/or using a cardholder or card provider selected technique(s) described herein.Bootloader 222 may only be active during a short interval after the card200 powers up. Card 200 may also be activated using program code thatmay be flashed directly to a microprocessor such as microcontroller 224,EMV chip 212, and/or the like. Card 200 may not use a bootloader 222 butinstead may cycle between a sleep state and an active state usingprogram code and/or memory.

A dynamic transaction card 200 may include a microcontroller 224 and anantenna 226. Antenna 226 may include, for example, a loop antenna, afractal antenna, and/or the like. Antenna 226 may transmit to andreceive signals from a mobile device, such as mobile device 140, toconduct transactions and display data as described throughout thespecification. Microcontroller 224 may communicate with EMV chip 212,Java Applet 208, Java Applet integration 210, sensor(s) 214, powermanagement 230, antenna 226, energy storage component 228, display 216,display driver 218, firmware 220, bootloader 222, and/or any othercomponent of dynamic transaction card 200. Microcontroller 224 maycontrol the card operations to conduct transactions and/or display dataas described throughout this specification. Microcontroller 224 maycontrol data collection and/or instruct data storage and/or transmissionassociated with the methods described herein.

Dynamic transaction card 200 may include an energy storage component 228that is integrated in a PCB 232. By way of example, energy storagecomponent 228 may include a lithium polymer battery, a lithium-metalbattery, lithium-ceramic battery, and/or any other type of battery,and/or power source. Energy storage component 228 may be constructed outof rigid materials, semiflexible materials, and/or flexible materials.Energy storage component 228 may provide power to card componentscontained within dynamic transaction card 200. Energy storage component228 may be a combine battery/potting component to support dynamictransaction card 200.

Dynamic transaction card 200 may include a power management component230 that may manage the charging and discharging of energy storagecomponent 228. Power management component 230 may convert voltage to apredetermined level in order to operate dynamic transaction card 200 asdiscussed throughout the specification. Power management component 230and/or energy storage component 228 may include, for example, solarpower cells to convert solar energy into an electrical current within asolar panel. Power management component 230 and/or energy storagecomponent 228 may include connections to sensors 214 to receive inputand activate dynamic transaction card 200 (e.g., motion input, thermalinput, manual input, touch input, and/or the like).

A flexible printed circuit board (PCB) 232 may be included in dynamictransaction card 200. A flexible PCB 232 may include a PCB mounted in aflexible plastic substrate, such as for example, a polyimide, polyetherether ketone, and/or a transparent conductive polyester film. A flexiblePCB 232 may be printed, using, for example screen printing, 3D printing,and/or the like, to arrange circuits on a material, such as polyester.Flexible PCB 232 may include electronic components and connections thatpower dynamic transaction card 200. Flexible PCB 232 may control and/orprovide integration between the components of card 200. For example,flexible PCB 232 mechanically supports and electronically connects theelectronic components of card 200 using, for example, conductive tracks,pads, and/or other features. A flexible printed circuit (FPC) may beused in place of or in conjunction with flexible PCB 232. FPC 232 may befabricated with photolithographic technology, such as light exposure ofa film material laminated to substrate and/or conductive layers. FPC 232may be printed, silkscreened, and/or the like. FPC 232 may be used as astructural member for the electronic components of card 200 and/or forthe card system as a whole 200.

Dynamic transaction card 200 may include a chassis 234 as a frame orsupporting structure. Chassis 234 may be a mount for a flexible PCB 232and may be constructed out of flexible or semi-flexible material aswell. Chassis 234 may be constructed out of a number of materials,including but not limited to, styrene, polycarbonate, polyester and PET.Chassis 234 may be constructed out of a conductive material. Chassis 234may increase the rigidity of dynamic transaction card 200 to preventdamage. Chassis 234 may also be used to detect if dynamic transactioncard 200 is being held by including sensors 214 around chassis 234.Where chassis 234 is constructed out of a conductive material, adielectric constant of chassis 234 and/or card 200 may be monitored todetect handling of card 200. Chassis 234 may be included within orseparate from a card backing 236. Card backing 236 may include amagnetic stripe that may be read using a magnetic stripe reader. Amagnetic strip may store tracks of data that are used to conduct atransaction using a dynamic transaction card 200. The tracks of data mayinclude a first track capable of storing alphanumeric characters as wellas symbols (e.g., ?, !, &, #, and/or the like), such as account numbers,account holder name, expiration data, security data, and/or otheraccount and/or card related data. The tracks of data may include asecond track capable of storing numeric characters such as accountnumbers, expiration data, security data, and/or other account and/orcard related data. The tracks of data may include a third track of datacapable of storing numeric characters such as an account number, a PIN,a country code, a currency code, an authorization amount, a balanceamount, and/or other account and/or card related data.

A magnetic stripe may be dynamically altered. For example, a dynamictransaction card 200 that is paired to a mobile device via, for example,Bluetooth, BLE, RFID, and/or other wireless technologies, may receivenew track data. The new track data may be unformatted, encrypted,encoded, and/or the like when the new track data is transmitted from themobile device to the dynamic transaction card 200. Upon receipt of thenew track data, the new track data may be routed to a microprocessor,such as EMV chip 212 and/or microcontroller 224. EMV chip 212 and/ormicrocontroller 224 may convert, decrypt, and/or decode the received newtrack data to ensure compliance with any standards. Once decrypted,decoded, and/or formatted, the new track data may be save on the tracksof the magnetic stripe. The magnetic stripe may be deleted and then thenew track data may be recorded onto the tracks. In this manner, trackdata stored on a magnetic stripe may be altered at any time upon pairinga dynamic transaction card 200 with a mobile device.

Card backing 236 may be made of similar material to that of the outputlayer 202 and/or the top protective layer 204. Card backing 236 may bemade out of a plastic material.

Although the components of dynamic transaction card 200 are illustratedin a particular fashion, these components may be combined and or placedthroughout a dynamic transaction card 200 in any manner, such as thosedepicted in, for example, FIG. 3.

For example, FIG. 3 illustrates an electric transaction card having anoutput layer 302 which may be similar to output layer 202; an outerprotective layer 304 which may be similar to outer protective layer 204;potting 306 which may be similar to potting 206; Java Applets 308 whichmay be similar to Java Applets 208; Java Applet integration 310 whichmay be similar to Java Applet integration 210; an EMV chip 312 which maybe similar to EMV chip 212; a sensor 314 which may be similar to sensor214; display 316 which may be similar to display 216; display driver 318which may be similar to display driver 218; firmware 320 which may besimilar to firmware 220; bootloader 322 which may be similar tobootloader 222; microcontroller 324 which may be similar tomicrocontroller 224; antenna 326 which may be similar to antenna 226;energy storage component 328 which may be similar to energy storagecomponent 228; power management 330 which may be similar to powermanagement 230; a flexible PCB 332 which may be similar to flexible PCB232; chassis 334 which may be similar to chassis 234; and/or cardbacking 336 which may be similar to card backing 236.

Returning to FIG. 1, backend system 130 may include a backend systemthat communicates with dynamic transaction card 120. For example, wheredynamic transaction card 120 is associated with a transaction card,backend system 130 may be a system associated with, for example, abanking service company such as Capital One®, Bank of America®,Citibank®, Wells Fargo®, Sun Trust, various community banks, and thelike, as well as a number of other financial institutions such as Visa®,MasterCard®, and American Express® that issue credit and/or debit cards,for example, as transaction cards. In this example, backend system 130may include and/or be connected to one or more computer systems andnetworks to process transactions.

Where an electronic device 120 is associated with a dynamic transactioncard, backend system 130 may include systems associated with financialinstitutions that issue transaction cards and maintains a contract withcardholders for repayment. In various embodiments, an backend system 130may issue a dynamic transaction card. Backend 130 may include, by way ofexample and not limitation, depository institutions (e.g., banks, creditunions, building societies, trust companies, mortgage loan companies,pre-paid gift cards or credit cards, etc.), contractual institutions(e.g., insurance companies, pension funds, mutual funds, etc.),investment institutions (e.g., investment banks, underwriters, brokeragefunds, etc.), electronics companies (e.g., electronics manufacturers,software providers, etc.), and other non-bank financial institutions(e.g., pawn shops or brokers, cashier's check issuers, insurance firms,check-cashing locations, payday lending, currency exchanges, microloanorganizations, crowd-funding or crowd-sourcing entities, third-partypayment processors, etc.).

Backend system 130 may include, among other components, an input/outputinterface 132 and various applications 134 that run the hardwareincluded in backend system 130. Input/output interface 132 may includefor example, I/O devices, which may be configured to provide inputand/or output to/from backend system 130 (e.g., keyboard, mouse,display, speakers, printers, modems, network cards, etc.). Input/outputinterface 132 also may include antennas, network interfaces that mayprovide or enable wireless and/or wire line digital and/or analoginterface to one or more networks, such as network 110, over one or morenetwork connections, a power source that provides an appropriatealternating current (AC) or direct current (DC) to power one or morecomponents of backend system 130, and a bus that allows communicationamong the various components of backend system 130. Input/outputinterface 132 may include a display, which may include for exampleoutput devices, such as a printer, display screen (e.g., monitor,television, and the like), speakers, projector, and the like. Althoughnot shown, each backend system 130 may include one or more encodersand/or decoders, one or more interleavers, one or more circular buffers,one or more multiplexers and/or de-multiplexers, one or more permutersand/or depermuters, one or more encryption and/or decryption units, oneor more modulation and/or demodulation units, one or more arithmeticlogic units and/or their constituent parts, and the like.

Applications 134 may include various hardware and software components tocommunicate between an electronic device 120, merchant system 150,and/or mobile device 140 in order to send/receive data and executefunctionality associate with electronic device 120. For example, whereelectronic device 120 is a dynamic transaction card, applications 134may be used to process a transaction using the dynamic transaction card.Backend system 130 may also include various hardware and softwarecomponents, such as data storage (not shown) to store data associatedwith an electronic device 120. For example, when an electronic device120 is a dynamic transaction card, backend system 130 may store a cardnumber, account type, account balance, account limits, budget data,recent transactions, pairing data such as time and date of pairing witha mobile device, and the like and/or cardholder data such as acardholder name, address, phone number(s), email address, demographicdata, and the like.

Applications 134 may include various hardware and software components touse data associated with a dynamic transaction card 120 as input tooptimize operational configurations and/or a user experience of thedynamic transaction card, detect system and/or device defects, andextend an energy storage life of the dynamic transaction card asdescribed herein, for example in FIGS. 6 and 7.

A mobile device 140 may be any device capable of communicating with adynamic transaction card 120 via, for example, Bluetooth technology, NFCtechnology, WiFi Direct technology, and/or the like. For example, mobiledevice 140 could be an iPhone, iPod, iPad, and/or Apple Watch fromApple® or any other mobile device running Apple's iOS operating system,any device running Google's Android® operating system, including, forexample, smartphones running the Android® operating system and otherwearable mobile devices, such as Google Glass or Samsung Galaxy GearSmartwatch, any device running Microsoft's Windows® Mobile operatingsystem, and/or any other smartphone or like device.

Mobile device 140 may include for example, an input/output interface142, a mobile application 144, and a power component 146. Input/outputinterface 142 may include, for example, a Bluetooth, RFID, and/or NFCinterface or chipset with a Bluetooth/RFID/NFC transceiver, a chip, andan antenna. The transceiver may transmit and receive information via theantenna and an interface. The chip may include a microprocessor thatstores and processes information specific to a transaction card deviceand provides device control functionality. Device control functionalitymay include connection creation, frequency-hopping sequence selectionand timing, power control, security control, polling, packet processing,and the like. The device control functionality and otherBluetooth/RFID/NFC-related functionality may be supported using aBluetooth/RFID/NFC API provided by the platform associated with themobile device 140 (e.g., The Android platform, the iOS platform). Usinga Bluetooth/RFID/NFC API, an application stored on a mobile device 140(e.g., a banking application, a financial account application, etc.) orthe device may be able to scan for other Bluetooth/RFID/NFC devices(e.g., a dynamic transaction card 120), query the localBluetooth/RFID/NFC adapter for paired Bluetooth/RFID/NFC devices,establish RFCOMM channels, connect to other devices through servicediscovery, transfer data to and from other devices (e.g., electronicdevice 120) and manage multiple connections. A Bluetooth API used in themethods, systems, and devices described herein may include an API forBluetooth Low Energy (BLE) to provide significantly lower powerconsumption and allow a mobile device 140 to communicate with BLEdevices that have low power requirements, such dynamic transaction card120.

Input/output interface 142 may include for example, I/O devices, whichmay be configured to provide input and/or output to mobile device 140(e.g., keyboard, mouse, display, speakers, printers, modems, networkcards, etc.). Input/output interface 142 also may include antennas,network interfaces that may provide or enable wireless and/or wire linedigital and/or analog interface to one or more networks, such as network110, over one or more network connections, a power source that providesan appropriate alternating current (AC) or direct current (DC) to powerone or more components of mobile device 140, and a bus that allowscommunication among the various components of mobile device 140.Input/output interface 142 may include a display, which may include forexample output devices, such as a printer, display screen (e.g.,monitor, television, and the like), speakers, projector, and the like.Although not shown, each mobile device 140 may include one or moreencoders and/or decoders, one or more interleavers, one or more circularbuffers, one or more multiplexers and/or de-multiplexers, one or morepermuters and/or depermuters, one or more encryption and/or decryptionunits, one or more modulation and/or demodulation units, one or morearithmetic logic units and/or their constituent parts, and the like.

Input/output interface 142 may also include an NFC antenna and secureelement (SE). The SE may be a hardware chip specially designed to betamper proof. In one embodiment, the SE may be used for digitally andphysically secure storage of sensitive data. For example, SE may be usedto store transaction card data, payment data, health records, car keyidentifiers, etc. The SE may, for example, store information related toa person, customer, financial institution, or other entity. The SE maystore information related to a financial account, such as, for example,transaction card data (e.g., a credit card number, debit account number,or other account identifier, account balance, transaction history,account limits, budget data, recent transactions, and/or the like). TheSE may include a computer processor or other computational hardware orsoftware. As one example, the secure element may contain the Visa® andMasterCard® applications for PayWave® and PayPass® transactions. Asecure element may take the form of a universal integrated circuit card(UICC) and/or a microSD card. A UICC may identify a user to a wirelessoperator, store contacts, enable secure connections, and add newapplications and services, such as a transaction engine that may includevarious components. These components may be understood to refer tocomputer executable software, firmware, hardware, and/or variouscombinations thereof.

Input/output interface 142 may enable Industry Standard NFC PaymentTransmission. For example, the input/output interface 142 may enable twoloop antennas to form an air-core transformer when placed near oneanother by using magnetic induction. Input/output interface 142 mayoperate at 13.56 MHz or any other acceptable frequency. Also,input/output interface 142 may provide for a passive communication mode,where the initiator device provides a carrier field, permitting answersby the target device via modulation of existing fields. Additionally,input/output interface 142 also may provide for an active communicationmode by allowing alternate field generation by the initiator and targetdevices.

Input/output interface 142 may deactivate the RF field while awaitingdata. The attachment may use Miller-type coding with varyingmodulations, including 100% modulation. The attachment may also useManchester coding with varying modulations, including a modulation ratioof 10%. Additionally, the attachment may be capable of receiving andtransmitting data at the same time, as well as checking for potentialcollisions when the transmitted signal and received signal frequenciesdiffer.

Input/output interface 142 may be capable of utilizing standardizedtransmission protocols, for example but not by way of limitation,ISO/IEC 14443 A/B, ISO/IEC 18092, MiFare, FeliCa, tag/smartcardemulation, and the like. Also, input/output interface 142 may be able toutilize transmission protocols and methods that are developed in thefuture using other frequencies or modes of transmission. Input/outputinterface 142 may also be backwards-compatible with existing techniques,for example RFID. Also, the system may support transmission requirementsto meet new and evolving standards including internet based transmissiontriggered by NFC.

Mobile applications 144 may include software and hardware componentsthat work with input/output interface 142 to generate and receiveaccount data associated with a dynamic transaction card 120. Forexample, applications 144 may include various hardware and softwarecomponents such as a processor and data storage to store data associatedwith dynamic transaction card 120. For example, data may include acardholder name, address, phone number(s), email address, demographicdata, card number, account type, account balance, account limits, budgetdata, recent transactions and the like.

Applications 144 may also facilitate the operation of mobile device 140.For example, mobile device 140 may include an operating system such as,for example, the iOS operating system from Apple, the Google Androidoperating system, and the Windows Mobile operating system fromMicrosoft. Mobile device 140 may also include, without limitation,software applications 144 such as mobile banking applications orfinancial institution applications to facilitate use of a dynamictransaction card 120, an NFC application programming interface, andsoftware to enable touch sensitive displays. Applications 144 mayinclude software stacks or Application Programming Interfaces (APIs)which allow software applications to be written on top of the softwarestacks. For example, mobile device manufacturers may provide, withoutlimitation, a card emulation API to enable NFC card emulation mode, alogic link control protocol (LLCP) API for peer-to-peer communicationbetween mobile devices, a Bluetooth API supporting BLE, and a real-timedata (RTD) API and a NFC Data Exchange Format (NDEF) API forreading/writing.

Applications 144 on mobile device 140, such as mobile bankingapplications and applications associated with dynamic transaction card120, may include on/off features that allow a user associated with amobile device 140 to enable and disable a dynamic transaction card 120.For example, where electronic device 120 is a dynamic transaction card,a card holder may use, for example, a mobile banking application storedon a mobile device 140 to disable and/or enable accounts associated witha dynamic transaction card 120.

Applications 144 may include various hardware and software components touse data associated with a dynamic transaction card 120 as input tooptimize operational configurations and/or a user experience of thedynamic transaction card, detect system and/or device defects, andextend an energy storage life of the dynamic transaction card asdescribed herein, for example in FIGS. 6 and 7.

Merchant system 150 may include, among other components, an input/outputinterface 152, application(s) 154, a transaction processor 156, and apower component 158. Merchant system 150 may also include data storage(not shown) to store data associated with the dynamic transaction card120.

An input/output interface 152 may include, for example, a transceiver,modems, network interfaces, buses, CD-ROM, keyboard, mouse, microphone,camera, touch screen, printers, USB flash drives, speakers, and/or anyother device configured to receive and transmit electronic data.Input/output interface 152 may include for example, I/O devices, whichmay be configured to provide input and/or output to and/or from merchantsystem 150 (e.g., keyboard, mouse, display, speakers, printers, modems,network cards, etc.). Input/output interface 152 also may includeantennas, network interfaces that may provide or enable wireless and/orwire line digital and/or analog interface to one or more networks, suchas network 110, over one or more network connections, a power sourcethat provides an appropriate alternating current (AC) or direct current(DC) to power one or more components of merchant system 150, and a busthat allows communication among the various components of merchantsystem 150. Input/output interface 152 may include a display, which mayinclude for example output devices, such as a printer, display screen(e.g., monitor, television, and the like), speakers, projector, and thelike. Although not shown, merchant system 150 may include one or moreencoders and/or decoders, one or more interleavers, one or more circularbuffers, one or more multiplexers and/or de-multiplexers, one or morepermuters and/or depermuters, one or more encryption and/or decryptionunits, one or more modulation and/or demodulation units, one or morearithmetic logic units and/or their constituent parts, and the like.

Applications 154 may include various software and/or hardware componentto enable merchant system 150 to charge and/or interact with a dynamictransaction card 120 (e.g., Bluetooth, RFID, NFC, etc.). Transactionprocessor 156 may include a slot or connection port (not shown) toenable the merchant system 150 to connect to dynamic transaction card120 (e.g., via contacts 122).

Merchant system 150 may also include a power component 158. Powercomponent 158 may include a microcontroller or integrated circuit thatgoverns power functions of merchant system 150. Power component 158 mayinclude a power source (e.g., a main battery or energy storage componentas described herein). Power component 158 also may include, for example,firmware, software, memory, a CPU, a CPU, input/output functions, timersto measure intervals of time, as well as analog to digital converters tomeasure the voltages of the main battery or energy storage component ofmerchant system 150. In various embodiments, power component 158 remainactive even when merchant system 150 is completely shut down, unused,and/or powered by the backup battery or energy storage component. Powercomponent 158 may be responsible for coordinating many functions,including, for example, monitoring power connections and battery orenergy storage component charges, charging batteries when necessary,controlling power to other integrated circuits within merchant system150 and/or other peripherals and/or readers, shutting down unnecessarysystem components when they are left idle, controlling sleep and powerfunctions (on and off), managing the interface for built-in keypad andtrackpads, and/or regulating a real-time clock (RTC).

FIG. 4 depicts an example PoS device 400 as a merchant system, which maybe similar to merchant system 150. PoS device 400 may provide theinterface at what a card holder makes a payment to the merchant inexchange for goods or services. PoS device 400 may include and/orcooperate with weighing scales, scanners, electronic and manual cashregisters, electronic funds transfer at point of sale (EFTPOS)terminals, touch screens and any other wide variety of hardware andsoftware available for use with PoS device 400. PoS device 400 may be aretail point of sale system and may include a cash register and/or cashregister-like computer components to enable purchase transactions. PoSdevice 400 also may be a hospitality point of sale system and includecomputerized systems incorporating registers, computers and peripheralequipment, usually on a computer network to be used in restaurant, hairsalons, hotels or the like.

PoS device 400 may be a wireless point of sale device similar to a PoSdevice described herein or, for example a tablet computer that isconfigured to operate as a PoS device, including for example, softwareto cause the tablet computer to execute point of sale functionality anda card reader such as for example the Capital One® SparkPay card reader,the Square® reader, Intuit's® GoPayment reader, or the like. In thisexample, PoS device 400 may be connected to a mobile device such thatthe mobile device may act as a merchant system 150. A mobile device mayinclude, for example, mobile device 140. PoS device 400 also may be acloud-based point of sale system that can be deployed as software as aservice, which can be accessed directly from the Internet using, forexample, an Internet browser.

Referring to FIG. 4, an example PoS device 400 is shown. PoS device 400may include a controller 402, a reader interface 404, a data interface406, a smartcard and/or EMV chip reader 408, a magnetic stripe reader410, a near-field communications (NFC) reader 412, a power manager 414,a keypad 416, an audio interface 418, a touchscreen/display controller420, and a display 422. Also, PoS device 400 may be coupled with,integrated into or otherwise connected with a cash register/retailenterprise system 424.

In various embodiments, Controller 402 may be any controller orprocessor capable of controlling the operations of PoS device 400. Forexample, controller 402 may be an Intel® 2nd Generation Core™ i3 or i5or Pentium™ G850 processor or the like. Controller 402 also may be acontroller included in a personal computer, smartphone device, tablet PCor the like.

Reader interface 404 may provide an interface between the various readerdevices associated with PoS device 400 and PoS device 400. For example,reader interface 404 may provide an interface between smartcard and/orEMV chip reader 408, magnetic stripe reader 410, NFC reader 412 andcontroller 402. In various embodiments, reader interface 404 may be awired interface such as a USB, RS232 or RS485 interface and the like.Reader interface 404 also may be a wireless interface and implementtechnologies such as Bluetooth, the 802.11(x) wireless specificationsand the like. Reader interface 404 may enable communication ofinformation read by the various reader devices from the various readerdevices to PoS device 400 to enable transactions. For example, readerinterface 404 may enable communication of a credit or debit card numberread by a reader device from that device to PoS device 400. In variousembodiments, reader interface 404 may interface between PoS device 400and other devices that do not necessarily “read” information but insteadreceive information from other devices.

Data interface 406 may allow PoS device 400 to pass communicate datathroughout PoS device and with other devices including, for example,cash register/retail enterprise system 424. Data interface 406 mayenable PoS device 400 to integrate with various customer resourcemanagement (CRM) and/or enterprise resource management (ERP) systems.Data interface 406 may include hardware, firmware and software that makeaspects of data interface 406 a wired interface. Data interface 406 alsomay include hardware, firmware and software that make aspects of datainterface 406 a wireless interface. In various embodiments, datainterface 406 also enables communication between PoS device otherdevices.

Smartcard and/or EMV chip reader 408 may be any electronic data inputdevice that connects to the contacts of an EMV chip on a transactioncard. Through these connections EMV chip reader 408 may transmit powerto the transaction card, read data from a transaction card and/or EMVchip, and send data to the transaction card and/or EMV chip. Smartcardand/or EMV chip reader 408 may be capable of supplying an integratedcircuit (e.g., EMV chip) on the transaction card with electricity andcommunicating with the transaction card via protocols, thereby enablingread and write functions. In various embodiments, smartcard and/or EMVchip reader 408 may enable reading from contact or contactlesstransaction cards. Smartcard and/or EMV chip reader 408 also maycommunicate using standard protocols including ISO/IEC 7816, ISO/IEC14443 and/or the like or proprietary protocols.

Magnetic stripe reader 410 may be any electronic data input device thatreads data from a magnetic stripe on a transaction card, for example. Invarious embodiments, magnetic stripe reader 410 may include a magneticreading head capable of reading information from a magnetic stripe.Magnetic stripe reader 410 may be capable of reading, for example,cardholder information from tracks 1, 2, and 3 on magnetic cards. Invarious embodiments, track 1 may be written on a card with code known asDEC SIXBIT plus odd parity and the information on track 1 may becontained in several formats (e.g., format A, which may be reserved forproprietary use of the card issuer; format B; format C-M which may bereserved for us by ANSI subcommittee X3B10; and format N-Z, which may beavailable for use by individual card issuers). In various embodiments,track 2 may be written with a 5-bit scheme (4 data bits plus 1 parity).Track 3 may be unused on the magnetic stripe. In various embodiments,track 3 transmission channels may be used for transmitting dynamic datapacket information to further enable enhanced token-based payments.

NFC reader 412 may be any electronic data input device that reads datafrom a NFC device. In an example embodiment, NFC reader 412 may enableIndustry Standard NFC Payment Transmission. For example, the NFC reader412 may communicate with a NFC enabled device to enable two loopantennas to form an air-core transformer when placed near one another byusing magnetic induction. NFC reader 412 may operate at 13.56 MHz or anyother acceptable frequency. Also, NFC reader 412 may enable a passivecommunication mode, where an initiator device provides a carrier field,permitting answers by the target device via modulation of existingfields. Additionally, NFC reader 412 also may enable an activecommunication mode by allowing alternate field generation by theinitiator and target devices.

In various embodiments, NFC reader 412 may deactivate an RF field whileawaiting data. NFC reader 412 may receive communications containingMiller-type coding with varying modulations, including 100% modulation.NFC reader 412 also may receive communications containing Manchestercoding with varying modulations, including a modulation ratio ofapproximately 10%, for example. Additionally, NFC reader 412 may becapable of receiving and transmitting data at the same time, as well aschecking for potential collisions when the transmitted signal andreceived signal frequencies differ.

NFC reader 412 may be capable of utilizing standardized transmissionprotocols, for example but not by way of limitation, ISO/IEC 14443 A/B,ISO/IEC 18092, MiFare, FeliCa, tag/smartcard emulation, and the like.Also, NFC reader 412 may be able to utilize transmission protocols andmethods that are developed in the future using other frequencies ormodes of transmission. NFC reader 412 also may be backwards-compatiblewith existing payment techniques, such as, for example RFID. Also, NFCreader 412 may support transmission requirements to meet new andevolving payment standards including internet based transmissiontriggered by NFC. In various embodiments, NFC reader 412 may utilizeMasterCard's® PayPass and/or Visa's® PayWave and/or American Express'®ExpressPay systems to enable transactions.

Although not shown and described, other input devices and/or readers,such as for example, barcode readers and the like are contemplated.

Power manager 414 may be any microcontroller or integrated circuit thatgoverns power functions of PoS device 400. Power manager 414 mayinclude, for example, firmware, software, memory, a CPU, a CPU,input/output functions, timers to measure intervals of time, as well asanalog to digital converters to measure the voltages of the main batteryor energy storage component of PoS device 400. In various embodiments,Power manager 414 remain active even when PoS device 400 is completelyshut down, unused, and/or powered by the backup battery or energystorage component. Power manager 414 may be responsible for coordinatingmany functions, including, for example, monitoring power connections andbattery or energy storage component charges, charging batteries whennecessary, controlling power to other integrated circuits within PoSdevice 400 and/or other peripherals and/or readers, shutting downunnecessary system components when they are left idle, controlling sleepand power functions (on and off), managing the interface for built-inkeypad and trackpads, and/or regulating a real-time clock (RTC).

Keypad 416 may any input device that includes a set of buttons arranged,for example, in a block or pad and may bear digits, symbols and/oralphabetical letters. Keypad 416 may be a hardware-based ormechanical-type keypad and/or implemented in software and displayed on,for example, a screen or touch screen to form a keypad. Keypad 416 mayreceive input from a user that pushed or otherwise activates one or morebuttons on keypad 416 to provide input.

Audio interface 418 may be any device capable of providing audio signalsfrom PoS device 400. For example, audio interface may be a speaker orspeakers that may produce audio signals. In various embodiments, audiointerface 418 may be integrated within PoS device 400. Audio interface418 also may include components that are external to PoS device 400.

Touchscreen/display control 420 may be any device or controller thatcontrols an electronic visual display. Touchscreen/display control 420may allow a user to interact with PoS device 400 through simple ormulti-touch gestures by touching a screen or display (e.g., display422). Touchscreen/display control 420 may be configured to control anynumber of touchscreens, including, for example, resistive touchscreens,surface acoustic wave touchscreens, capacitive touchscreens, surfacecapacitance touchscreens, projected capacitance touchscreens, mutualcapacitance touchscreens, self-capacitance touchscreens, infrared gridtouchscreens, infrared acrylic projection touchscreens, opticaltouchscreens, touchscreens based on dispersive signal technology,acoustic pulse recognition touchscreens, and the like. In variousembodiments, touchscreen/display control 420 may receive inputs from thetouchscreen and process the received inputs. Touchscreen/display control420 also may control the display on PoS device 400, thereby providingthe graphical user interface on a display to a user of PoS device 400.

Display 422 may be any display suitable for a PoS device. For example,display 422 may be a TFT, LCD, LED or other display. Display 422 alsomay be a touchscreen display that for example allows a user to interactwith PoS device 400 through simple or multi-touch gestures by touching ascreen or display (e.g., display 422). Display 422 may include anynumber of touchscreens, including, for example, resistive touchscreens,surface acoustic wave touchscreens, capacitive touchscreens, surfacecapacitance touchscreens, projected capacitance touchscreens, mutualcapacitance touchscreens, self-capacitance touchscreens, infrared gridtouchscreens, infrared acrylic projection touchscreens, opticaltouchscreens, touchscreens based on dispersive signal technology,acoustic pulse recognition touchscreens, and the like. In variousembodiments, 422 may receive inputs from control gestures provided by auser. Display 422 also may display images, thereby providing thegraphical user interface to a user of PoS device 400.

Cash register/retail enterprise system 424 may me any device or devicesthat cooperate with PoS device 400 to process transactions. Cashregister/retail enterprise system 424 may be coupled with othercomponents of PoS device 400 via, for example, a data interface (e.g.,data interface 406) as illustrated in FIG. 4. Cash register/retailenterprise system 424 also may be integrated into PoS device 400.

In various embodiments, cash register/retail enterprise system 424 maybe a cash register. Example cash registers may include, for example,mechanical or electronic devices that calculate and record salestransactions. Cash registers also may include a cash drawer for storingcash and may be capable of printing receipts. Cash registers also may beconnected to a network to enable payment transactions. Cash registersmay include a numerical pad, QWERTY or custom keyboard, touch screeninterface, or a combination of these input methods for a cashier toenter products and fees by hand and access information necessary tocomplete the sale.

In various embodiments, cash register/retail enterprise system 424 maycomprise an retail enterprise system and/or a customer relationshipmanagement system. Retail enterprise system 424 may enable retainenterprises to manage operations and performance across a retailoperation. Retail enterprise system 424 may be a stand-alone applicationin, for example, individual stores, or may be interconnected via anetwork. Retail enterprise system 424 may include various point of salecapabilities, including the ability to, for example, customize andresize transaction screens, work with a “touch screen” graphical userinterface, enter line items, automatically look up price (sales,quantity discount, promotional, price levels), automatically computetax, VAT, look up quantity and item attribute, display item picture,extended description, and sub-descriptions, establish default shippingservices, select shipping carrier and calculate shipping charges byweight/value, support multi-tender transactions, including cash, check,credit card, and debit card, accept food stamps, place transactions onhold and recall, perform voids and returns at PoS, access online creditcard authorizations and capture electronic signatures, integrate debitand credit card processing, ensure optional credit card discounts withaddress verification, support mix-and-match pricing structure, discountentire sale or selected items at time of sale, add customer account,track customer information, including total sales, number of visits, andlast visit date. issue store credit, receive payment(s) for individualinvoices, process deposits on orders, search by customer's ship-toaddress, create and process layaway, back orders, work orders, and salesquotes, credit items sold to selected sales reps, view daily sales graphat the PoS, view and print journals from any register, preview, search,and print journals by register, batch, and/or receipt number, print X,Z, and ZZ reports, print receipts, invoices, and pick tickets withlogos/graphics, print kit components on receipt, reprint receipts, enteremployee hours with an integrated time clock function, and/or sell whenthe network/server is down with an offline PoS mode. Retail enterprisesystem 424 also may include inventory control and tracking capabilities,reporting tools, customer management capabilities, employee managementtools, and may integrate with other accounting software.

In various embodiments cash register/retail enterprise system 424 may bea hospitality PoS. In such embodiments, retail enterprise system 424 mayinclude hospitality PoS software (e.g., Aloha PoS Restaurant softwarefrom NCR®, Micros® RES and Symphony software and the like), hospitalitymanagement software, and other hardware and software to facilitatehospitality operations.

Returning to FIG. 1, backend system 130 may include a backend systemthat communicates with a mobile device 140 as described in FIG. 5. Forexample, system 500 may include a user device 502, which may be similarto mobile device 140, a network 504, which may be similar to network110, a front-end controlled domain 506, a back-end controlled domain512, and a backend 518, which may be similar to backend system 130.Front-end controlled domain 506 may include one or more load balancers508 and one or more web servers 510. Back-end controlled domain 512 mayinclude one or more load balancers 514 and one or more applicationservers 516.

User device 502 may be a network-enabled computer. As referred toherein, a network-enabled computer may include, but is not limited to:e.g., any computer device, or communications device including, e.g., aserver, a network appliance, a personal computer (PC), a workstation, amobile device, a phone, a handheld PC, a personal digital assistant(PDA), a thin client, a fat client, an Internet browser, or otherdevice. The one or more network-enabled computers of the example system400 may execute one or more software applications to enable, forexample, network communications.

User device 502 may include an iPhone, iPod, iPad, and/or Apple Watchfrom Apple® or any other mobile device running Apple's iOS operatingsystem, any device running Google's Android® operating system, includingfor example, Google's wearable device, Google Glass, any device runningMicrosoft's Windows® Mobile operating system, and/or any othersmartphone or like wearable mobile device.

Network 504 may be one or more of a wireless network, a wired network,or any combination of a wireless network and a wired network. Forexample, network 404 may include one or more of a fiber optics network,a passive optical network, a cable network, an Internet network, asatellite network, a wireless LAN, a Global System for MobileCommunication (GSM), a Personal Communication Service (PCS), a PersonalArea Networks, (PAN), D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b,802.15.1, 802.11n, and 802.11g or any other wired or wireless networkfor transmitting and receiving a data signal.

In addition, network 504 may include, without limitation, telephonelines, fiber optics, IEEE Ethernet 902.3, a wide area network (WAN), alocal area network (LAN) or a global network such as the Internet. Also,network 504 may support an Internet network, a wireless communicationnetwork, a cellular network, or the like, or any combination thereof.Network 504 may further include one network, or any number of exampletypes of networks mentioned above, operating as a stand-alone network orin cooperation with each other. Network 504 may utilize one or moreprotocols of one or more network elements to which they arecommunicatively couples. Network 504 may translate to or from otherprotocols to one or more protocols of network devices. Although network504 is depicted as a single network, it should be appreciated thataccording to one or more embodiments, network 404 may comprise aplurality of interconnected networks, such as, for example, theInternet, a service provider's network, a cable television network,corporate networks, and home networks.

Front-end controlled domain 506 may be implemented to provide securityfor backend 518. Load balancer(s) 508 may distribute workloads acrossmultiple computing resources, such as, for example computers, a computercluster, network links, central processing units or disk drives. Invarious embodiments, load balancer(s) 510 may distribute workloadsacross, for example, web server(s) 516 and/or backend 518 systems. Loadbalancing aims to optimize resource use, maximize throughput, minimizeresponse time, and avoid overload of any one of the resources. Usingmultiple components with load balancing instead of a single componentmay increase reliability through redundancy. Load balancing is usuallyprovided by dedicated software or hardware, such as a multilayer switchor a Domain Name System (DNS) server process.

Load balancer(s) 508 may include software that monitoring the port whereexternal clients, such as, for example, user device 502, connect toaccess various services of a financial institution, for example. Loadbalancer(s) 508 may forward requests to one of the application servers516 and/or backend 518 servers, which may then reply to load balancer508. This may allow load balancer(s) 508 to reply to user device 502without user device 502 ever knowing about the internal separation offunctions. It also may prevent mobile devices from contacting backendservers directly, which may have security benefits by hiding thestructure of the internal network and preventing attacks on backend 518or unrelated services running on other ports, for example.

A variety of scheduling algorithms may be used by load balancer(s) 508to determine which backend server to send a request to. Simplealgorithms may include, for example, random choice or round robin. Loadbalancers 508 also may account for additional factors, such as aserver's reported load, recent response times, up/down status(determined by a monitoring poll of some kind), number of activeconnections, geographic location, capabilities, or how much traffic ithas recently been assigned.

Load balancers 508 may be implemented in hardware and/or software. Loadbalancer(s) 508 may implement numerous features, including, withoutlimitation: asymmetric loading; Priority activation: SSL Offload andAcceleration; Distributed Denial of Service (DDoS) attack protection;HTTP/HTTPS compression; TCP offloading; TCP buffering; direct serverreturn; health checking; HTTP/HTTPS caching; content filteringHTTP/HTTPS security; priority queuing; rate shaping, content-awareswitching; client authentication; programmatic traffic manipulation;firewall; intrusion prevention systems.

Web server(s) 510 may include hardware (e.g., one or more computers)and/or software (e.g., one or more applications) that deliver webcontent that can be accessed by, for example a client device (e.g., userdevice 502) through a network (e.g., network 504), such as the Internet.In various examples, web servers, may deliver web pages, relating to,for example, online banking applications and the like, to clients (e.g.,user device 502). Web server(s) 510 may use, for example, a hypertexttransfer protocol (HTTP/HTTPS or sHTTP) to communicate with user device502. The web pages delivered to client device may include, for example,HTML documents, which may include images, style sheets and scripts inaddition to text content.

A user agent, such as, for example, a web browser, web crawler, ornative mobile application, may initiate communication by making arequest for a specific resource using HTTP/HTTPS and web server 510 mayrespond with the content of that resource or an error message if unableto do so. The resource may be, for example a file on stored on backend518. Web server(s) 510 also may enable or facilitate receiving contentfrom user device 502 so user device 502 may be able to, for example,submit web forms, including uploading of files.

Web server(s) also may support server-side scripting using, for example,Active Server Pages (ASP), PHP, or other scripting languages.Accordingly, the behavior of web server(s) 510 can be scripted inseparate files, while the actual server software remains unchanged.

Load balancers 514 may be similar to load balancers 408 as describedabove.

Application server(s) 516 may include hardware and/or software that isdedicated to the efficient execution of procedures (e.g., programs,routines, scripts) for supporting its applied applications. Applicationserver(s) 516 may comprise one or more application server frameworks,including, for example, Java application servers (e.g., Java platform,Enterprise Edition (Java EE), the .NET framework from Microsoft®, PHPapplication servers, and the like). The various application serverframeworks may contain a comprehensive service layer model. Also,application server(s) 516 may act as a set of components accessible to,for example, a financial institution, or other entity implementingsystem 500, through an API defined by the platform itself. For Webapplications, these components may be performed in, for example, thesame running environment as web server(s) 510, and application servers416 may support the construction of dynamic pages. Application server(s)516 also may implement services, such as, for example, clustering,fail-over, and load-balancing. In various embodiments, where applicationserver(s) 516 are Java application servers, the web server(s) 516 maybehaves like an extended virtual machine for running applications,transparently handling connections to databases associated with backend518 on one side, and, connections to the Web client (e.g., user device402) on the other.

Backend 518 may include hardware and/or software that enables thebackend services of, for example, a financial institution, merchant, orother entity that maintains a distributed system similar to system 500.For example, backend 518 may include, a system of record, online bankingapplications, encryption applications, BLE/Bluetooth connectionplatforms, a rewards platform, a payments platform, a lending platform,including the various services associated with, for example, auto andhome lending platforms, a statement processing platform, one or moreplatforms that provide mobile services, one or more platforms thatprovide online services, a card provisioning platform, a general ledgersystem, and/or a location system, which may include additionalcapabilities, such as transaction card data generation, transactionprocessing, and/or transmission of account and/or transaction data.Backend 518 may be associated with various databases, including accountdatabases that maintain, for example, cardholder information (e.g.,demographic data, credit data, cardholder profile data, and the like),transaction card databases that maintain transaction card data (e.g.,transaction history, account balance, spending limit, budget categories,budget spending, budget limits, and the like), connection information(e.g., public/private key pairs, UUIDs, device identifiers, and thelike) and the like. Backend 518 also may be associated with one or moreservers that enable the various services provided by system 500. Backend518 may enable a financial institution to implement various functionsassociated with reprogramming a transaction card and/or providing datato a dynamic transaction card to provide optimal configurations asdescribed herein.

For example, FIGS. 6 and 7 illustrate example methods that use dataassociated with a dynamic transaction card as input to optimizeoperational configurations and/or a user experience of the dynamictransaction card, detect system and/or device defects, and extend anenergy storage life of the dynamic transaction card.

Process 600 may begin at block 602. At block 604, a dynamic transactioncard may use a microcontroller and/or sensor within the dynamictransaction card to monitor configuration and/or functionality data.Configuration and/or functionality data associated with the powercomponents may include, for example, sensor input (e.g., a number oftaps, a number of double taps, time between double taps, fingerprint,PIN or password input, light sensor threshold, and/or the like),connection data (e.g., connection attempts, connection length, time inadvertising mode, time in scanning mode, and/or the like), transactiondata (e.g., contactless transaction attempts, time per contactlesstransaction, contact transaction attempts, time per contacttransactions, and/or the like), display data (e.g., light brightness,light active time, display brightness, display contrast, display activetime, and/or the like), and/or the like.

Dynamic transaction card may transmit configuration and/or functionalitydata to a mobile device, merchant system, and/or backend system via thesystems and/or methods described herein, utilizing JSON and/or XML. Forexample, configuration and/or functionality data may be transmitted to amobile device, merchant system, and/or backend system as a portion oftransaction data, such as metadata. In this manner, mobile device,merchant system, and/or backend system may monitor configuration and/orfunctionality data. Dynamic transaction card users may be segmented intouser groups based on similar card usage patterns and deviceconfigurations, and the associated configuration and/or functionalitydata may clustered together for each user group segment for optimalconfiguration processing to generate an optimal configuration per usergroup segment, which may utilize an alternating least squares algorithm.The transaction card user segmentation may be automatically updated inreal time base on changes in card usage and/or device configurations. Inblock 606, the configuration and/or functionality data may be stored.Configuration and/or functionality data may be stored in a dynamictransaction card, such as in a microprocessor, EMV chip, and/or datastorage. Configuration and/or functionality data may be stored in datastorage associated with a merchant system, backend system, and/or mobiledevice.

Transmission of data between a dynamic transaction card and a userdevice and/or backend system may be performed at any interval. Forexample, transmission of data may occur on an hourly, daily, and/orother timed interval. Transmission of data may occur on an event basis,such as at each transaction, a number of transactions, a number ofpower-ups of a dynamic transaction card, a number of waking-ups of adynamic transaction card, and/or the like.

In block 608, optimal configurations may be calculated by a processorusing the configuration and/or functionality data. Optimalconfigurations may be determined by linear regression, logisticregression, ridge regression, lasso regression, Bayesian regression,machine learning algorithms, and/or the like. Optimal configurations maybe calculated on a device-by-device basis, a grouping of devices (e.g.,grouping by demographic data, grouping by geolocation data, grouping byusage, grouping by software revisions, grouping by hardware differencessuch as a device generation, and/or the like), and or the entirety ofdynamic transaction cards. Optimal configurations may include adisplay/lighting brightness, a display/lighting contrast, a sensorsensitivity threshold, a time between receiving input and sleeping, atime between receiving input and disconnecting from a network, and/orthe like.

Optimization of data may be performed at any interval. For example,optimization of data may occur on an hourly, daily, and/or other timedinterval. Optimization of data may occur on an event basis, such as anumber of transactions, a number of power-ups of a dynamic transactioncard, a number of waking-ups of a dynamic transaction card, and/or thelike.

Extended energy storage life and/or a particular user experience may bedetermined based on the optimal configurations. For example, theconfiguration and/or functionality data may be optimized in order todetermine a maximum energy storage life for a dynamic transaction card,promote various behaviors, and/or detect system and/or device defects.For example, to extend an energy storage life, various lighting,brightness, and/or power usage card settings may be altered. As anotherexample, a user experience may be optimized based on card configurationand/or functionality data by comparing configurations and/orfunctionality data (e.g., time a balance is illuminated on a carddisplay, number of alerts displayed per transaction, and/or the like)associated with a particular user behavior stored in a backend system(e.g., sticking to a budget, always paying a bill on time, maintaining aparticular balance, and/or the like). In this manner, where a particularconfiguration and/or functionality of a card results in a particularbehavior and/or a high likelihood of achieving a particular behavior,the particular configuration and/or functionality data associated withthe behavior may be pushed to a card, a grouping of cards, and/or anentirety of cards in order to optimize the desired user behavior.Configuration and/or functionality data may be optimized in order todetermine a maximum transaction attempts. Without the data generated bythe dynamic transaction card(s), the dynamic transaction cards may notbe optimized in order to determine defects and/or optimize an energystorage life and/or user experience.

At block 610, optimal configurations may be transmitted from a processorvia a network to at least one dynamic transaction card. The optimalconfigurations may be transmitted to a particular transaction card, aparticular grouping of transaction cards, and/or an entirety of dynamictransaction cards. Optimal configurations may be transmitted via anetwork connection as described herein. Optimal configurations may bepushed to a dynamic transaction card using an EMV Issuer script. Forexample, an EMV Issuer script may be used to update and/or changeconfigurations and/or values on the EMV chip. An EMV Issuer script mayinclude an Issuer Script Identifier and/or an Issuer Script Command,which may be received in, for example, an authorization responsemessage. A terminal (e.g., a merchant system, a mobile device, and/orthe like) may apply the EMV Issuer script during the completion of atransaction via the contacts of an EMV chip. In this manner, an issuer(e.g., backend system) alters EMV chip using data (e.g., optimalconfiguration data and/or values).

At block 612, configuration and/or functionality data may be monitoredby a dynamic transaction card associated with the transmitted optimalconfigurations, similar to the monitoring in block 604. In this manner,configuration and/or functionality data may be continuously monitoredand optimized to promote a desired card functionality and/or userbehavior. At block 614, the process may end.

Process 700 may begin at block 702. At block 704, dynamic transactioncard may use a microcontroller within the dynamic transaction card tomonitor configuration and/or functionality data. Configuration and/orfunctionality data associated with the power components may include, forexample, sensor input (e.g., a number of taps, a number of double taps,time between double taps, fingerprint, PIN or password input, lightsensor threshold, and/or the like), connection data (e.g., connectionattempts, connection length, time in advertising mode, time in scanningmode, and/or the like), transaction data (e.g., contactless transactionattempts, time per contactless transaction, contact transactionattempts, time per contact transactions, and/or the like), display data(e.g., light brightness, light active time, display brightness, displaycontrast, display active time, and/or the like), and/or the like.

Dynamic transaction card may transmit via a network configuration and/orfunctionality data to mobile device, merchant system, and/or backendsystem via the systems and/or methods described herein. In this manner,mobile device, merchant system, and/or backend system may monitorconfiguration and/or functionality data. Transmission of data between adynamic transaction card and a user device and/or backend system may beperformed at any interval. For example, transmission of data may occuron an hourly, daily, and/or other timed interval. Transmission of datamay occur on an event basis, such as a number of transactions, a numberof power-ups of a dynamic transaction card, a number of waking-ups of adynamic transaction card, and/or the like.

In block 706, the configuration and/or functionality data may be stored.Configuration and/or functionality data may be stored in a dynamictransaction card, such as in a microprocessor, EMV chip, and/or datastorage. Configuration and/or functionality data may be stored in datastorage associated with a merchant system, backend system, and/or mobiledevice. Configuration and/or functionality data may be transmitted tovia a network and stored on a mobile device, merchant system, and/orbackend system as a portion of transaction data, such as metadata.

In block 708, optimal configurations may be calculated by a processorusing the configuration and/or functionality data. Optimalconfigurations may be determined by linear regression, logisticregression, ridge regression, lasso regression, Bayesian regression,machine learning algorithms, and/or the like. Optimal configurations maybe calculated on a device-by-device basis, a grouping of devices basedon cluster segmentation (e.g., grouping by demographic data, grouping bygeolocation data, grouping by usage, grouping by software revisions,grouping by hardware differences such as a device generation, and/or thelike), and or the entirety of dynamic transaction cards. Optimalconfigurations may include a display/lighting brightness, adisplay/lighting contrast, a sensor sensitivity threshold, a timebetween receiving input and sleeping, a time between receiving input anddisconnecting from a network, and/or the like.

Optimal configurations may be based on a desired user behavior. Forexample, a user experience may be optimized based on card configurationand/or functionality data by comparing configurations and/orfunctionality data (e.g., time a balance is illuminated on a carddisplay, number of alerts displayed per transaction, and/or the like)associated with a particular user behavior stored in a backend system(e.g., sticking to a budget, always paying a bill on time, maintaining aparticular balance, and/or the like). In this manner, a system maydetermine that a particular configuration and/or functionality of a cardresults in a particular behavior and/or a high likelihood of achieving aparticular behavior.

At block 710, outliers may be identified based on the calculated optimalconfigurations by a processor. Outliers may indicate a system defectassociated with a particular mobile device and/or merchant system suchas a network defect resulting in an extended network connection time, asystem defect resulting in extended transaction times, and/or the like.Outliers may indicate device defects and/or user error. System defectsmay be determined by determining and detecting outlier data associatedwith transaction card transaction data. Device defects and/or user errormay be determined by determining and detecting outlier data associatedwith any configuration and/or functionality data for a particulardevice.

At block 712, outlier data including any potential defect explanationand/or alerts may be transmitted from a processor via a network to adevice associated with the outlier, a backend system associated with adevice having outlier data, and/or a mobile device associated with adevice having outlier data. In this manner, devices with defects may bemarked, monitored, replaced, and/or repaired based on the detecteddefect. Where a device with a defect and/or user error includes adynamic transaction card, defect and/or user error data may betransmitted to a dynamic transaction card using EMV Issuer scripts. Forexample, an EMV Issuer script may be used to update and/or changeconfigurations and/or values (e.g., display values) stored on the EMVchip. An EMV Issuer script may include an Issuer Script Identifierand/or an Issuer Script Command, which may be received in, for example,an authorization response message. A terminal (e.g., a merchant system,a mobile device, and/or the like) may apply the EMV Issuer script duringthe completion of a transaction via the contacts of an EMV chip. In thismanner, an issuer (e.g., backend system) alters EMV chip using data(defect and/or error data). At block 714, the process may end.

The present disclosure is not to be limited in terms of the particularembodiments described in this application, which are intended asillustrations of various aspects. Many modifications and variations canbe made without departing from its spirit and scope, as may be apparent.Functionally equivalent methods and apparatuses within the scope of thedisclosure, in addition to those enumerated herein, may be apparent fromthe foregoing representative descriptions. Such modifications andvariations are intended to fall within the scope of the appendedrepresentative claims. The present disclosure is to be limited only bythe terms of the appended representative claims, along with the fullscope of equivalents to which such representative claims are entitled.It is also to be understood that the terminology used herein is for thepurpose of describing particular embodiments only, and is not intendedto be limiting.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity.

It may be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It may be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent may be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to embodiments containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should be interpreted to mean “at least one”or “one or more”); the same holds true for the use of definite articlesused to introduce claim recitations. In addition, even if a specificnumber of an introduced claim recitation is explicitly recited, suchrecitation should be interpreted to mean at least the recited number(e.g., the bare recitation of“two recitations,” without other modifiers,means at least two recitations, or two or more recitations).Furthermore, in those instances where a convention analogous to “atleast one of A, B, and C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, and C”would include but not be limited to systems that have A alone, B alone,C alone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). In those instances where a conventionanalogous to “at least one of A, B, or C, etc.” is used, in general sucha construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, or C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It may be furtherunderstood by those within the art that virtually any disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms. For example, the phrase “A or B” may be understood toinclude the possibilities of “A” or “B” or “A and B.”

The foregoing description, along with its associated embodiments, hasbeen presented for purposes of illustration only. It is not exhaustiveand does not limit the invention to the precise form disclosed. Thoseskilled in the art may appreciate from the foregoing description thatmodifications and variations are possible in light of the aboveteachings or may be acquired from practicing the disclosed embodiments.For example, the steps described need not be performed in the samesequence discussed or with the same degree of separation. Likewisevarious steps may be omitted, repeated, or combined, as necessary, toachieve the same or similar objectives. Accordingly, the invention isnot limited to the above-described embodiments, but instead is definedby the appended claims in light of their full scope of equivalents.

In the preceding specification, various preferred embodiments have beendescribed with references to the accompanying drawings. It may, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe broader scope of the invention as set forth in the claims thatfollow. The specification and drawings are accordingly to be regarded asan illustrative rather than restrictive sense.

1. A dynamic transaction card comprising: a microcontroller within thedynamic transaction card; data storage within the dynamic transactioncard storing optimal configurations; wherein: the microcontroller:monitors a plurality of hardware components of the dynamic transactioncard in order to determine functionality data and a plurality ofsoftware configurations used to derive configuration data; transmits,via a network, the functionality data and configuration data to aprocessor that utilizes machine learning to cluster functionality and/orconfiguration data to process the functionality data and configurationdata with respect to a user group segment; receives, via the network,optimal configuration data from the processor; and applies the optimalconfigurations to the dynamic transaction card.
 2. The dynamictransaction card of claim 1, wherein the processor calculates theoptimal configuration data by maximizing energy storage length using thefunctionality data and configuration data as variables.
 3. The dynamictransaction card of claim 1, wherein the processor calculates theoptimal configuration data by determining a desired user behavior,determining a probability that a particular functionality data and aparticular configuration data results in the desired user behavior, andwhere the probability is higher than a predetermined threshold,assigning the configuration data as the optimal configuration data. 4.The dynamic transaction card of claim 1, further comprising a sensorthat monitors a plurality of hardware components of the dynamictransaction card in order to determine functionality data and aplurality of software configurations in order to determine configurationdata.
 5. The dynamic transaction card of claim 4, wherein thefunctionality data and configuration data comprise sensor input,connection data, transaction data, and/or display data.
 6. The dynamictransaction card of claim 1, wherein the optimal configurations arecalculated at the processor by determining a desired user behavior,determining a probability that a particular functionality data and aparticular configuration data results in the desired user behavior, andwhere the probability is higher than a predetermined threshold,assigning the configuration data as the optimal configuration data. 7.The dynamic transaction card of claim 1, wherein the dynamic transactioncard and/or data storage associated with a merchant system, a backendsystem and/or a mobile device stores functionality data and/orconfiguration data.
 8. The dynamic transaction card of claim 1, whereinthe optimal configurations are calculated at the processor by linearregression, logistic regression, ridge regression, lasso regression,Bayesian regression, machine learning algorithms.
 9. The dynamictransaction card of claim 1, wherein the optimal configurations arecalculated on a transaction card basis, a grouping of transaction cardbasis, and/or an entirety of transaction card basis.
 10. The dynamictransaction card of claim 1, wherein the functionality and configurationdata are optimized to determine a maximum number of transactionattempts.
 11. The dynamic transaction card of claim 1, wherein themicrocontroller transmits functionality data, configuration data and/oroptimal configurations at a timed interval and/or on an event basis. 12.The dynamic transaction card of claim 1, wherein the optimalconfigurations are pushed to the dynamic transaction card using aEuroPay-MasterCard-Visa (EMV) Issuer script.
 13. The dynamic transactioncard of claim 1, wherein the microcontroller continuously monitors thefunctionality data, configuration data, and/or optimal configurations.14. The dynamic transaction card of claim 1, wherein the processordetects system and/or device defects by determining outlier dataassociated with dynamic transaction card data and outlier dataassociated with functionality and/or configuration data.
 15. The dynamictransaction card of claim 14, wherein the outlier data is transmittedvia a network to the dynamic transaction card, a backend system and/or amobile device associated with the dynamic transaction card.
 16. Amethod, comprising: monitoring, using a microcontroller within a dynamictransaction card, a plurality of hardware components of the dynamictransaction card in order to determine functionality data and aplurality of software configurations used to derive configuration data;transmitting, via a network, the functionality data and configurationdata to a processor; utilizing machine learning to cluster functionalityand/or configuration data to process the functionality data andconfiguration data with respect to a user group segment; calculating,using a processor, optimal configuration data; storing, in data storagewithin the dynamic transaction card, the optimal configurations; andapplying, using the microcontroller, the optimal configurations to thedynamic transaction card.
 17. The method of claim 16, wherein theoptimal configurations are calculated at the processor by maximizingenergy storage length using the functionality data and configurationdata as variables.
 18. The method of claim 16, wherein the optimalconfigurations are calculated at the processor by determining a desireduser behavior, determining a probability that a particular functionalitydata and a particular configuration data results in the desired userbehavior, and where the probability is higher than a predeterminedthreshold, assigning the configuration data as the optimal configurationdata.
 19. The method of claim 16, wherein the functionality data andconfiguration data comprise sensor input, connection data, transactiondata, and/or display data.
 20. The method of claim 16, furthercomprising storing the functionality data and/or configuration data inthe dynamic transaction card and/or data storage associated with amerchant system, a backend system and/or a mobile device.
 21. The methodof claim 16, wherein the optimal configurations are calculated at theprocessor by linear regression, logistic regression, ridge regression,lasso regression, Bayesian regression, machine learning algorithms. 22.The method of claim 16, wherein the optimal configurations arecalculated on a transaction card basis, a grouping of transaction cardbasis, and/or an entirety of transaction card basis.
 23. The method ofclaim 16, wherein the functionality and configuration data are optimizedto determine a maximum number of transaction attempts.
 24. The method ofclaim 16, wherein the transmitting of functionality data, configurationdata and/or optimal configurations are performed at a timed intervaland/or on an event basis.
 25. The method of claim 16, further comprisingpushing the optimal configurations to the dynamic transaction card usinga EuroPay-MasterCard-Visa (EMV) Issuer script.
 26. The method of claim25, further comprising applying the EMV Issuer script during thecompletion of a transaction via contacts of an EMV chip within thedynamic transaction card.
 27. The method of claim 16, further comprisingcontinuously monitoring the functionality data, configuration data,and/or optimal configurations.
 28. The method of claim 16, furthercomprising detecting system and/or device defects by determining outlierdata associated with dynamic transaction card data and outlier dataassociated with functionality and/or configuration data.
 29. The methodof claim 28, further comprising transmitting the outlier data via anetwork to the dynamic transaction card, a backend system and/or amobile device associated with the dynamic transaction card.